Dec 01 09:31:52.674 INFO testing mersinvald/batch_resolve against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 01 09:31:52.674 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-1/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 09:31:53.030 INFO [stdout] bf2a6cf508e867398da35b16f8878848574779229e03e8dc07ae6b3a999a8ae6
Dec 01 09:31:53.033 INFO running `"docker" "start" "-a" "bf2a6cf508e867398da35b16f8878848574779229e03e8dc07ae6b3a999a8ae6"`
Dec 01 09:31:54.440 INFO [stderr] usermod: no changes
Dec 01 09:31:54.501 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:31:54.501 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:31:54.501 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:31:54.501 INFO [stderr] files will be included as a binary target:
Dec 01 09:31:54.501 INFO [stderr] 
Dec 01 09:31:54.501 INFO [stderr] * /source/src/main.rs
Dec 01 09:31:54.501 INFO [stderr] 
Dec 01 09:31:54.501 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:31:54.501 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:31:54.501 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:31:54.501 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:31:54.501 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:31:54.501 INFO [stderr] 
Dec 01 09:31:54.501 INFO [stderr] For more information on this warning you can consult
Dec 01 09:31:54.501 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:31:54.501 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `batch_resolve`,
Dec 01 09:31:54.501 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 09:31:54.746 INFO [stderr]    Compiling openssl v0.9.11
Dec 01 09:31:54.751 INFO [stderr]    Compiling trust-dns v0.10.1
Dec 01 09:31:54.751 INFO [stderr]    Compiling serde v1.0.3
Dec 01 09:31:54.751 INFO [stderr]    Compiling data-encoding v1.2.0
Dec 01 09:31:54.751 INFO [stderr]    Compiling iovec v0.1.0
Dec 01 09:31:54.762 INFO [stderr]    Compiling net2 v0.2.29
Dec 01 09:31:54.763 INFO [stderr]    Compiling clicolors-control v0.1.0
Dec 01 09:31:54.771 INFO [stderr]    Compiling parking_lot_core v0.2.1
Dec 01 09:31:56.595 INFO [stderr]    Compiling clap v2.24.1
Dec 01 09:31:56.655 INFO [stderr]    Compiling bytes v0.4.3
Dec 01 09:31:56.767 INFO [stderr]    Compiling serde_derive_internals v0.15.0
Dec 01 09:31:58.258 INFO [stderr]    Compiling chrono v0.2.25
Dec 01 09:31:58.431 INFO [stderr]    Compiling error-chain v0.1.12
Dec 01 09:32:05.620 INFO [stderr]    Compiling mio v0.6.7
Dec 01 09:32:05.739 INFO [stderr]    Compiling parking_lot v0.4.3
Dec 01 09:32:05.739 INFO [stderr]    Compiling tokio-io v0.1.1
Dec 01 09:32:06.063 INFO [stderr]    Compiling serde_derive v1.0.3
Dec 01 09:32:13.187 INFO [stderr]    Compiling indicatif v0.1.0
Dec 01 09:32:16.682 INFO [stderr]    Compiling tokio-core v0.1.7
Dec 01 09:32:34.837 INFO [stderr]    Compiling toml v0.4.0
Dec 01 09:33:01.799 INFO [stderr]    Compiling batch_resolve_cli v0.3.5 (/source)
Dec 01 09:33:03.545 INFO [stderr] warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods instead
Dec 01 09:33:03.545 INFO [stderr]    --> src/resolve/batch.rs:110:1
Dec 01 09:33:03.545 INFO [stderr]     |
Dec 01 09:33:03.545 INFO [stderr] 110 | / arg_enum!{
Dec 01 09:33:03.545 INFO [stderr] 111 | |     #[derive(Copy, Clone, Debug)]
Dec 01 09:33:03.545 INFO [stderr] 112 | |     pub enum QueryType {
Dec 01 09:33:03.545 INFO [stderr] 113 | |         A,
Dec 01 09:33:03.545 INFO [stderr] ...   |
Dec 01 09:33:03.545 INFO [stderr] 117 | |     }
Dec 01 09:33:03.545 INFO [stderr] 118 | | }
Dec 01 09:33:03.545 INFO [stderr]     | |_^
Dec 01 09:33:03.545 INFO [stderr]     |
Dec 01 09:33:03.545 INFO [stderr]     = note: #[warn(deprecated)] on by default
Dec 01 09:33:03.545 INFO [stderr]     = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Dec 01 09:33:03.545 INFO [stderr] 
Dec 01 09:33:14.411 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1m 19s
Dec 01 09:33:14.427 INFO [stderr] su: No module specific data is present
Dec 01 09:33:15.498 INFO running `"docker" "inspect" "bf2a6cf508e867398da35b16f8878848574779229e03e8dc07ae6b3a999a8ae6"`
Dec 01 09:33:15.847 INFO running `"docker" "rm" "-f" "bf2a6cf508e867398da35b16f8878848574779229e03e8dc07ae6b3a999a8ae6"`
Dec 01 09:33:16.164 INFO [stdout] bf2a6cf508e867398da35b16f8878848574779229e03e8dc07ae6b3a999a8ae6
Dec 01 09:33:16.169 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-1/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 09:33:16.595 INFO [stdout] e851a78553c22e500328adef85d248289ee34c921f9ec2c765bf0f9fb7226387
Dec 01 09:33:16.597 INFO running `"docker" "start" "-a" "e851a78553c22e500328adef85d248289ee34c921f9ec2c765bf0f9fb7226387"`
Dec 01 09:33:17.955 INFO [stderr] usermod: no changes
Dec 01 09:33:18.003 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:33:18.003 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:33:18.003 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:33:18.003 INFO [stderr] files will be included as a binary target:
Dec 01 09:33:18.003 INFO [stderr] 
Dec 01 09:33:18.003 INFO [stderr] * /source/src/main.rs
Dec 01 09:33:18.003 INFO [stderr] 
Dec 01 09:33:18.003 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:33:18.003 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:33:18.003 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:33:18.003 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:33:18.003 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:33:18.003 INFO [stderr] 
Dec 01 09:33:18.003 INFO [stderr] For more information on this warning you can consult
Dec 01 09:33:18.003 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:33:18.003 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `batch_resolve`,
Dec 01 09:33:18.003 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 09:33:18.143 INFO [stderr]    Compiling batch_resolve_cli v0.3.5 (/source)
Dec 01 09:33:19.615 INFO [stderr] warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods instead
Dec 01 09:33:19.615 INFO [stderr]    --> src/resolve/batch.rs:110:1
Dec 01 09:33:19.615 INFO [stderr]     |
Dec 01 09:33:19.615 INFO [stderr] 110 | / arg_enum!{
Dec 01 09:33:19.615 INFO [stderr] 111 | |     #[derive(Copy, Clone, Debug)]
Dec 01 09:33:19.615 INFO [stderr] 112 | |     pub enum QueryType {
Dec 01 09:33:19.615 INFO [stderr] 113 | |         A,
Dec 01 09:33:19.615 INFO [stderr] ...   |
Dec 01 09:33:19.615 INFO [stderr] 117 | |     }
Dec 01 09:33:19.615 INFO [stderr] 118 | | }
Dec 01 09:33:19.615 INFO [stderr]     | |_^
Dec 01 09:33:19.615 INFO [stderr]     |
Dec 01 09:33:19.615 INFO [stderr]     = note: #[warn(deprecated)] on by default
Dec 01 09:33:19.615 INFO [stderr]     = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Dec 01 09:33:19.615 INFO [stderr] 
Dec 01 09:33:20.963 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.97s
Dec 01 09:33:20.979 INFO [stderr] su: No module specific data is present
Dec 01 09:33:21.685 INFO running `"docker" "inspect" "e851a78553c22e500328adef85d248289ee34c921f9ec2c765bf0f9fb7226387"`
Dec 01 09:33:22.061 INFO running `"docker" "rm" "-f" "e851a78553c22e500328adef85d248289ee34c921f9ec2c765bf0f9fb7226387"`
Dec 01 09:33:22.475 INFO [stdout] e851a78553c22e500328adef85d248289ee34c921f9ec2c765bf0f9fb7226387
Dec 01 09:33:22.477 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-1/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 09:33:23.060 INFO [stdout] 5411592cd90d1cefe7049218c639c46cb7df51bcefea820b816e61a890d242b8
Dec 01 09:33:23.064 INFO running `"docker" "start" "-a" "5411592cd90d1cefe7049218c639c46cb7df51bcefea820b816e61a890d242b8"`
Dec 01 09:33:24.338 INFO [stderr] usermod: no changes
Dec 01 09:33:24.395 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:33:24.395 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:33:24.395 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:33:24.395 INFO [stderr] files will be included as a binary target:
Dec 01 09:33:24.395 INFO [stderr] 
Dec 01 09:33:24.395 INFO [stderr] * /source/src/main.rs
Dec 01 09:33:24.395 INFO [stderr] 
Dec 01 09:33:24.395 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:33:24.395 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:33:24.395 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:33:24.395 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:33:24.395 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:33:24.395 INFO [stderr] 
Dec 01 09:33:24.395 INFO [stderr] For more information on this warning you can consult
Dec 01 09:33:24.395 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:33:24.395 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `batch_resolve`,
Dec 01 09:33:24.395 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 09:33:24.589 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.22s
Dec 01 09:33:24.607 INFO [stderr]      Running /target/debug/deps/batch_resolve-ba8dfe6488a374a2
Dec 01 09:33:24.621 INFO [stdout] 
Dec 01 09:33:24.621 INFO [stdout] running 0 tests
Dec 01 09:33:24.621 INFO [stdout] 
Dec 01 09:33:24.621 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 09:33:24.621 INFO [stdout] 
Dec 01 09:33:24.627 INFO [stderr] su: No module specific data is present
Dec 01 09:33:26.024 INFO running `"docker" "inspect" "5411592cd90d1cefe7049218c639c46cb7df51bcefea820b816e61a890d242b8"`
Dec 01 09:33:26.294 INFO running `"docker" "rm" "-f" "5411592cd90d1cefe7049218c639c46cb7df51bcefea820b816e61a890d242b8"`
Dec 01 09:33:26.771 INFO [stdout] 5411592cd90d1cefe7049218c639c46cb7df51bcefea820b816e61a890d242b8
